Communications Process Flow

Each communication results in the comm being sent to one target. Multiple targets, such as sending an email to all subscriptions on an accountClosed In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices., is not currently supported.

The communications process is as follows:

ClosedA communication request is triggered

The Communications process starts when a communication request is triggered. A trigger can be:

When a trigger is invoked, CMP creates an entry in the core table in Communications, the Comms Request Header table.

When a Workflow Event is created, irrespective on whether the WhenToCreate is set to OnCreate or OnResolve, an entry in created in the Comms Request Header.

ClosedCommunication details are gathered

When an entry is created in the Comms Request Header table, the Comms Monitor Job is triggered to process the Comms Request Header and produce a Comms Request Detail. This job:

ClosedSMS and push and online notifications are sent

After the Comms Monitor Job has completed, dedicated daemons pick up the requests to distribute them to the destination:

  • Comms SMS Daemon
  • Comms Push To Handset Daemon
  • Comms Push To External Daemon

ClosedLetters and emails are created and sent

Email and letter communications require additional processing to merge data from default fields gathered from CMP with document templates to generate the required document type. The Comms Monitor job gathers the data; the Comms Email Monitor and the Comms Letter Monitor jobs merge the data.

The Comms Email Monitor and Comms Letter Monitor jobs are triggered automatically when the Comms Monitor job has finished gathering data for Comms Requests relating to emails or letters.

These jobs uses external frameworks - for example, Velocity and Prince XMLClosed Exstensible Markup Language. A markup language used to describe data that allows users to define their information formats, especially in order to display documents on the Internet. - to generate documents. Generated documents are subsequently detected by the following downstream daemons for transmission to the customer:

  • Comms Email Daemon
  • Comms Letter Daemon

ClosedLetters and emails are stored

This is a distinct step carried out by the Comms Storage Daemon. This allows the documents to be placed into storage on any machine, for example, in systems such as Amazon S3 or on a machine via SFTPClosed Secure File Transfer Protocol. A network protocol used for secure file transfer between remote systems over a secure shell.. Storing the documents in a long-term storage directory allows them to be viewed in AgentViewClosed The graphical user interface of the CMP that is typically used by Customer Service Agents to access CMP customer and billing data. In versions prior to CMP 8.0, this was called the CMP GUI..

ClosedExternal systems update communications status

An APIClosed Application Programming Interface. A set of functions and procedures that allow the creation of applications that access the features or data of another software system, such as an application or operating system. allows external systems to update the status in CMP of communications that were sent externally for processing and/or distribution.

Related Topics Link IconRelated Topics